Release 10.1A: OpenEdge Application Server:
Administration

Enabling the WSA for HTTPS client connections

OpenEdge supports Secure Socket Layer (SSL)-enabled communications between the Web server where the WSA runs and a Web service client. To achieve this, you must enable the WSA for HTTPS (SSL) connections.

Note: The procedure that follows pertains to the security of communication between the client application and the WSA. To enable SSL communication between the WSA and the AppServer, you must obtain and install public key certificates for the WSA host machine and complete separate configuration procedures for each deployed service and for the AppServer. See the "Security considerations for Web service administration" section for more information.

To enable the WSA for SSL:

Obtain a private key and a Web server digital certificate.
Enable and configure the Web server for SSL support.

This includes installing the Web server digital certificate in the Web server. For more information, see the Web server documentation.

Using a text editor, modify the web.xml file for the WSA as follows:

In the <security-context> element for WSA administration, located in the <transport-guarantee> element, change the value from NONE to CONFIDENTIAL.

Note: For more information on web.xml, see Chapter 5, " WSA administration architecture."
Using a text editor, edit the ubroker.properties file to set the WSA URL (value of the wsaUrl property) to use the HTTPS protocol (instead of HTTP).